-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ice: mDNS refactoring #934
Conversation
5462187
to
722db91
Compare
I'm a bit unsure how we should handle this nicely. Without Trickle we have to wait for all candidates. But mDNS timeouts are between 3-5 seconds. That's a high startup delay. Especially if hosts are not on the same network. Should we migrate baresip ice to trickle and add only mDNS support there? |
There are two ICE stacks, "ice" and "trice". The latter one has multiple interfaces and supports Trickle ICE, it has been in production We could create a new baresip module Waiting for all candidates to finish it not so practical, IMHO. You could also add a new flag |
It is also possible to add optional "Trickle Mode" to the current ICE stack, so that we |
There is also another solution, which is to set the mDNS timeout short, e.g. 100ms. |
722db91
to
02529e2
Compare
Since I had already a 100ms default timeout implemented this workaround was easy. Needs some testing... |
02529e2
to
69c4b4c
Compare
mDNS resolving can lead to long timeouts (~5s), so it's better to resolve IPv4 and IPv6 separately to avoid long ice startup delays.
69c4b4c
to
f6e4bdf
Compare
No description provided.